Timestamp-based security device registration

ABSTRACT

A method of registering a security sensor device with a product device to be protected via the security sensor device includes obtaining sensor data identifying the security sensor device and including a sensor timestamp for an alteration in power delivery to the security sensor device, obtaining product data identifying the product device and including a product timestamp for an alteration in power delivery to the product device, implementing a comparison of the sensor timestamp and the product timestamp, and generating registration data for the security sensor device and the product device based on the comparison, the registration data associating the security sensor device and the product device.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of co-pending U.S. patent applicationSer. No. 16/177,856, filed Nov. 1, 2018, the entire disclosure of whichis hereby incorporated by reference.

BACKGROUND OF THE DISCLOSURE Field of the Disclosure

The disclosure relates generally to security devices for products ondisplay.

Brief Description of Related Technology

Products are often displayed in retail environments with a securitydevice. The security device prevents or deters theft while giving aconsumer an opportunity to evaluate the product. The security device isoften affixed to the product to help keep the product in a specificposition in a display area. The security device nonetheless typicallyallows the consumer to lift or otherwise inspect the product to assessits function and/or aesthetics. Allowing the consumer to lift theproduct gives the consumer a better opportunity to assess the weight andfeel of the product, as well as interact with the various features andother aspects of the product.

SUMMARY OF THE DISCLOSURE

In accordance with one aspect of the disclosure, a method of registeringa security sensor device with a product device to be protected via thesecurity sensor device. The method includes obtaining, by a networkedcomputing device, sensor data identifying the security sensor device andincluding a sensor timestamp for an alteration in power delivery to thesecurity sensor device, obtaining, by the networked computing device,product data identifying the product device and including a producttimestamp for an alteration in power delivery to the product device,implementing, by the networked computing device, a comparison of thesensor timestamp and the product timestamp, and generating, by thenetworked computing device, registration data for the security sensordevice and the product device based on the comparison, the registrationdata associating the security sensor device and the product device.

In accordance with another aspect of the disclosure, a method ofregistering a security sensor device with a product device to beprotected via the security sensor device. The method includes obtaining,by a networked computing device, a sensor data package including sensoridentification data, display location data, and sensor power event data,the display location data being indicative of a location of a productdisplay in which the product device is displayed, the sensor power eventdata being indicative of an alteration in delivery of power to thesecurity sensor device, obtaining, by the networked computing device, aproduct data package including product identification data and productpower event data, the product power event data being indicative of analteration in delivery of power to the product device, implementing, bythe networked computing device, a comparison of respective timestamps ofthe sensor power event data and the product power event data, and if therespective timestamps match, generating, by the networked computingdevice, registration data for the security sensor device and the productdevice based on the sensor identification data and the productidentification data, the registration data associating the securitysensor device, the location of the product display, and the productdevice.

In accordance with another aspect of the disclosure, a networkedcomputing device for registration of a security sensor device and aproduct device to be protected by the security sensor device. Thenetworked computing device includes a processor, a memory in whichcorrelation instructions and database management instructions are storedfor execution by the processor, a storage device configured to storeregistration data associating the security sensor device and the productdevice, where the processor is configured via the execution of thecorrelation instructions to obtain, from the security sensor device viaa first network communication, a sensor data identifying the securitysensor device and includes a sensor timestamp for an alteration in powerdelivery to the security sensor device, obtain, from the product devicevia a second network communication, product data identifying the productdevice and including a product timestamp for an alteration in powerdelivery to the product device, implement a comparison of the sensortimestamp and the product timestamp, and generate the registration datafor the security sensor device and the product device based on thecomparison, and wherein the processor is configured via the execution ofthe database management instructions to store the registration data inthe storage device.

In connection with any one of the aforementioned aspects, the methodsand devices described herein may alternatively or additionally includeany combination of one or more of the following aspects or features. Thealteration in power delivery to the security sensor device includes apower connection or disconnection between the security sensor device anda display location via which power is delivered to the security sensordevice. The sensor data includes display location data. The displaylocation data is indicative of a location of a product display in whichthe product device is displayed. The registration data furtherassociates the display location data with the security sensor device andthe product device. The display location data identifies a cradleconfigured to receive the security sensor device. The display locationidentifies a plan-o-gram position of the location of the productdisplay. The sensor data includes site location data indicative of asite in which the product display is located. The registration furtherassociates the site location data with the security sensor device andthe product device. The sensor data and the product data include sensorpower event data and product power event data indicative of thealteration in power delivery to the security sensor device and theproduct device, respectively. The sensor power event data is indicativeof whether the alteration in power delivery involves either a start oran end of power delivery to the security sensor device. The productpower event data is indicative of whether the alteration in powerdelivery involves either a start or an end of power delivery to theproduct device. Implementing the comparison includes determining whetherboth the sensor power event data and the product power event data matchregarding whether the alteration in power delivery involves either astart or an end of power delivery. Implementing the comparison includesdetermining whether the sensor timestamp and the product timestampmatch. Generating the registration data includes associating the sensordata and the product data if the comparison reveals that the sensortimestamp and the product timestamp match. Obtaining the sensor dataincludes receiving a sensor data package including sensor identificationdata and sensor power event data. Obtaining the product data includesreceiving a product data package including product identification dataand product power event data. Obtaining the sensor data includesreceiving a sensor data package from the security sensor device via analarm control unit at a site in which the product device is located.Obtaining the product data includes receiving a product data packagefrom the product device via a service executing on the product device.Implementing the comparison includes determining whether both the sensorpower event data and the product power event data match regardingwhether the alteration in power delivery involves either a start or anend of power delivery. The registration data is generated if the sensorpower event data and the product power event data match regardingwhether the alteration in power delivery involves either a start or anend of power delivery. Generating the registration data includes sendingthe registration data to a network storage device for storage of theregistration data in a registration database. The method furtherincluding storing, in the registration database, customer interactiondata in association with the registration data, the customer interactiondata involving a customer interaction with the product device. Theprocessor is configured via the execution of the correlationinstructions to generate the registration data such that theregistration data associates the display location data with the securitysensor device and the product device. The processor is configured viathe execution of the correlation instructions to determine whether boththe sensor power event data and the product power event data matchregarding whether the alteration in power delivery involves either astart or an end of power delivery.

BRIEF DESCRIPTION OF THE DRAWING FIGURES

For a more complete understanding of the disclosure, reference should bemade to the following detailed description and accompanying drawingfigures, in which like reference numerals identify like elements in thefigures.

FIG. 1 is a perspective view of a system having a security sensor deviceto protect a product device in which registration of the security sensordevice is implemented in accordance with one example.

FIG. 2 is a perspective view of the system of FIG. 1 to depict acomputer-readable marking of the security sensor device for registrationof the security sensor device in accordance with one example.

FIG. 3 is a block diagram of a system for registration of securitysensor devices, product devices, and product display locations inaccordance with one example.

FIG. 4 is a flow diagram of a method of registration of security sensordevices, product devices, and product display locations in accordancewith one example.

FIG. 5 is a block diagram of a system for timestamp-based, automaticregistration of security sensor devices, product devices, and productdisplay locations in accordance with one example.

FIG. 6 is a flow diagram of a method of timestamp-based, automaticregistration of security sensor devices, product devices, and productdisplay locations in accordance with one example.

FIG. 7 is a flow diagram of a method of automatic un-registration ofsecurity sensor devices, product devices, and product display locationsin accordance with one example.

The disclosed systems and methods are susceptible of embodiments invarious forms. There are illustrated in the drawing (and will hereafterbe described) specific embodiments of the invention, with theunderstanding that the disclosure is intended to be illustrative, and isnot intended to limit the invention to the specific embodimentsdescribed and illustrated herein.

DETAILED DESCRIPTION OF THE DISCLOSURE

Systems and methods for registering security sensor devices with productdevices protected thereby are described. The systems and methodsassociate a respective one of the security sensor devices with arespective one of the product devices. Registration data indicative ofthe association, or registration, may then be stored for networkedaccess and use. In some cases, the registration data is used tofacilitate the collection and analysis of data regarding customerinteraction with the respective product device, such as the number,frequency, duration, and other characteristics of product lifts. Theregistration data may be useful in a variety of other ways, including,for instance, the collection, tracking, monitoring, or other use ofinformation regarding position, alarm, or other status of a productdevice.

The registration data provided by the disclosed systems and methods maysupport associations beyond pairing security sensor devices and productdevices. A respective security sensor device and a respective productdevice may also be registered or associated with a product displaylocation. The registration data may thus indicate a specific locationwithin a retail environment at which the security sensor device and/orproduct device are disposed. For instance, the specific location withinand/or of a particular display base or cradle may be identified. Suchregistration data is useful in helping to keep product devices in aspecific, desired position on a product display apparatus. Suchregistration data may be useful in other ways, including, for instance,determining which respective physical locations correspond with higheror lower evaluation activity or other consumer interaction.

Various techniques for obtaining identification data underlying theregistration data are described. In some cases, computer-readablemarkings, such as quick response (QR) codes, are scanned to obtainidentification data for the security sensor device, the product device,and/or the product display location. Other types of markings or visualcoding may be used, including, for instance, bar codes. Optical scannersor readers may be used to capture the identification data.

Other techniques for obtaining the identification data involve wirelesscommunications. The wireless communications may be established by orwith dedicated scanners or readers. Alternatively or additionally, thewireless communications do not involve separate scanners, but insteaduse a more direct communication link, such as a link between therespective security sensor device and the respective product device. Thesecurity sensor device and/or the product device may thus be configuredto act as a scanner or reader in such cases. Still other techniques forobtaining the identification data may not involve wirelesscommunications, including, for instance, techniques involvingtransmission of product location or other identification data via atether, cable, or other connection between, e.g., a product displaycradle or other base and a security sensor device.

The extent, frequency, and other circumstances under which theidentification data is obtained may vary considerably. In some cases,the collection of the identification data may be initiated by a storeemployee operating a scanner. Other scanning may be scheduled orotherwise conducted automatically. Alternatively or additionally, theidentification data is obtained upon the detection of an event, such asthe attachment of a security sensor device and a product device.

The registration data may be transmitted for networked storage andaccess. In some cases, the networked storage includes or involves adatabase managed by a remote server. The remote server may be configuredto implement data analytics on data indicative of customer interactionwith the product device. For example, data including the quantity oftimes a certain product is evaluated, the frequency of evaluations, therespective times of day of each evaluation and/or the duration of eachrespective evaluation, and/or the respective physical position on thedisplay that correspond to higher or lower evaluation activity, all mayassist retailers and/or manufacturers in quantifying consumer interestin a certain product. The remote server may also be configured tofacilitate user access to results of the data analytics, including, forinstance, via mobile phone application or other user.

Although described in connection with tracking customer interaction, thedisclosed systems and methods are not limited to usage scenariosinvolving data analytics on customer-product interaction. Theregistration data may be useful in connection with a wide variety ofcontexts and issues arising in product device display scenarios. Forinstance, the registration data may be useful in connection with retailsetup compliance. Some retail stores set up and take down productdisplays daily. In such cases, the registration data may assist storeemployees in correctly positioning the products across all of theproduct displays. The registration data may also be useful in othercompliance monitoring, including, for instance, stock-out compliance, inwhich the registration data is used to detect or identify out-of-stockproducts.

FIGS. 1 and 2 illustrate a system 10 that provides security sensor andother registration data in accordance with one example. In this case,the system 10 has three example product devices 14A, 14B, 14C. In thiscase, all three product devices 14A-C are positioned and/or located on adisplay platform 16. The display platform 16 and the product devices14A-14C may be located, for example, in a retail store, for consumerevaluation. Hereinafter, the product 14A, the product 14B and/or theproduct 14C may be collectively referred to as the product device 14.The product device 14 may be a portable electronic device, such as, forexample, a cellular telephone, tablet computer, MP3 player, camera, GPSdevice and the like. However, the product 14 may be any device displayedand/or sold at, for example, a retail store. For example, the product 14may be or include a non-electronic device.

The system 10 includes a number of security sensor devices 12 to providesecurity for the product devices 14A-C. Each security sensor device 12may be affixed or otherwise coupled to a respective one of the products14, for example, via an adhesive, and may dock to a respective cradle orbase 18. The cradle 18 may be located on the display platform 16. Thecradle 18 may have a recess 18A in which the security device 12 isreceived. For example, the security device 12 may have an extendedportion 12A that docks within the recess 18A of the cradle 18. When thesecurity device 12 is docked, the cradle 18 may provide power to and/orcharge the security device 12 and/or the product 14. On the displayplatform 16, the product device 14 and/or the security device 12 may bepresented in a docked position, i.e., the product 14 and/or the securitydevice 12 may be docked to the cradle 18.

A consumer may lift the product device 14 and the security sensor device12 from the cradle 18 and the platform 12, as shown in FIG. 2. In thiscase, the lift of the product device 14 results in a corresponding liftof the security sensor device 12. The consumer may then evaluate theproduct device 14 and, when finished, return the product device 14 tothe cradle 18.

The configuration of the system 10 and the display platform 16 maydiffer from the example shown. For instance, in some cases, the system10 includes one or more posts extending upward from the display platform16. One of the cradles 18 may then be mounted or otherwise disposed atthe end of the post. The posts allow the product devices to be furtherspaced from the display platform 16. In still other cases, the securitysensor device 12 tethers the product 14 to the display 16. For example,a retractable cable (not shown) may extend from the security device 12to the base 18. The cradle 18 and/or the retractable cable may providepower to the security sensor device 12 and/or to the product device 14.In some cases, the retractable cable may be disconnected from thesecurity sensor device 12 via a key.

The system 10 includes a number of other components in communicationwith the security sensor device 12 to provide security for the productdevices 14. In the example of FIG. 1, the system 10 includes ananalytics, communications, or other data module 11, an alarm module 13,and an emitter 15. Other examples may have fewer or additionalcomponents on site with the product devices, as described below inconnection with the example of FIG. 3. To maintain security when thesecurity sensor device 12 is detached from the retractable cable and/orthe base 18, the security sensor device 12 wirelessly communicates withthe alarm module 13 and/or the emitter 15. Data communication among thevarious components within the system 10 may be implemented in accordancewith a wireless standard networking protocol, e.g. IEEE 802.11. The datamodule 11, the alarm module 13 and/or the emitter 15 may be positionednear the display 16 of the product 14. As shown in FIG. 2, a computer19, such as, for example, a laptop computer, may be positioned near thedisplay 16, and may be connected to the data module 11, the alarm module13 and/or the emitter 15.

Security for the product device 14 is provided in accordance with oneexample as follows. The alarm module 13 may be programmed to transmit asignal (e.g., a high frequency signal) to the emitter 15 to request theemitter 15 to transmit a signal (e.g., a low frequency signal) to thesecurity sensor devices 12. If the security sensor device 12 is withinrange of the emitter 15, the security sensor device 12 may receive thelow frequency signal 31 from the emitter 15 that may request thesecurity sensor device 12 to transmit a signal to the alarm module 13.The security sensor device 12 may be programmed to then transmit a highfrequency signal 32 to the alarm module 13 that indicates that thesecurity device 12 is located within a range of the emitter 15.Alternatively, if the security sensor device 12 is located outside ofthe range of the emitter 15, the security sensor device 12 fails toreceive the low frequency signal 31 from the emitter 15 and thus failsto transmit the high frequency signal 32 to the alarm module 13. Thealarm module 13 may be programmed to produce an audio alarm and/or avisual alarm if the alarm module 13 fails to receive the high frequencysignal 32 from the security sensor device 12. Additionally, the securitysensor device 12 may be programmed to emit an audio alarm and/or avisual alarm if the security sensor device 12 fails to receive the lowfrequency signal 31 from the emitter 15. Further details regardingexamples of the alarm module 13 and the emitter 15 are set forth in U.S.Patent Publication No. 2016/0307415 (“Apparatus, System and Method forMonitoring a Device within a Zone”), the entire disclosure of which ishereby incorporated by reference.

The manner in which the security sensor device 12 and other componentsof the system 10 provide security may vary from the above-describedexample. For example, the alarm module 13 may alternatively oradditionally monitor a received signal strength indicator (RSSI) of awireless signal transmitted from the security sensor device 12 todetermine the proximity of the security sensor device 12 to the alarmmodule 13 and/or the emitter 14. Alternatively or additionally, thesecurity device 12, the emitter 14, and/or the alarm module 13 maycommunicate via ultra-wideband signals. In these and other cases, thedistance between the security sensor device 12, the emitter 14, and/orthe alarm module 13 may be determined by monitoring a time of flight(TOF) of the various wireless signals between the various transceivers.

The data module 11 (and/or other components, as described below) may beprogrammed to monitor, collect, or otherwise communicate or process datawithin the system 10. In some cases, the data module 11 may include atransceiver to transmit and receive wireless signals to receive dataregarding interactions with the product devices 14. The data module 11may include a microprocessor or other processor programmed to monitor,log, or otherwise capture or process data communicated in the system 10.For example, the data module 11 may be programmed to capture datatransmitted from the security sensor device 12, the alarm module 13and/or the emitter 15. In some cases, the data module 11 may beconnected to the alarm module 13. In other cases, some of thefunctionality of the data module 11 is provided remotely (e.g., by aremote server), as described below. In such and other cases, the datamodule 11 may include a router or other network gateway component(s).

The data module 11 (or processor thereof) may be programmed tomanipulate the captured data and/or to determine statistical data. Thestatistical data may be indicative of various characteristics of theconsumer interaction with the product devices of the product display.For example, the statistical data may be indicative of a quantity oflifts of the product device, a frequency of lifts of the product deviceand/or a duration of lifts of the product device. A clock of the datamodule 11 may identify the time of day of a lift, the time of day of areturn and/or may time a lift duration. Further details regardingexamples of the statistical data and analysis thereof are set forth inU.S. Patent Publication No. 2016/0308952 (“Apparatus, System and Methodfor Wirelessly Collecting Data Corresponding to a Security Device”), theentire disclosure of which is hereby incorporated by reference.

The security sensor device 12 (or processor thereof) may be programmedto detect or otherwise determine a position status, alarm status, and/orother status of the security sensor device 12. The security sensordevice 12 (or processor thereof) may be further programmed to wirelesslytransmit the status data to other component(s) of the system 10, e.g.,using a high frequency signal. Examples of the status data includeposition status of the security device 12, alarm status of the securitydevice 12, and/or other status data. In some cases, the security device12 may be electrically connected to a port (not shown) of the productdevice 14 via, for example, a USB or other cable. Disconnection of thesecurity sensor device 12 from the product device 14 and/or removal ofthe cable from the port of the security sensor device 12 may activate analarm of the security sensor device 12. The alarm may be or include anaudio alarm and/or a visual alarm. In the docked position, as shown inFIG. 1, the security sensor device 12 and/or the product device 14 mayreceive power via the cradle 18 and/or the retractable cable. The alarmof the security sensor device 12 may activate if a transceiver of thesecurity device 12, for example, fails to receive a low frequency signalfrom the emitter 15.

The alarm module 13 may include a transceiver to transmit and/or receivewireless signals. A processor of the alarm module 13 may be programmedto detect signals (e.g., the above-described high frequency signal)and/or transmit, via the transceiver, other signals (e.g., theabove-described high frequency signal). The processor may be programmedto activate an alarm during an alarm condition of the alarm module 13and/or of the security sensor device 12. The alarm may be or include anaudio alarm and/or a visual alarm.

The emitter 15 may include a transceiver to transmit and/or receivewireless signals. The emitter 15 may further include a processor (notshown) that may be programmed to receive and/or detect signals, such asthe above-described high frequency signal from the alarm module.Further, the processor of the emitter 15 may be programmed to transmit,via the transceiver of the emitter 15, signals, such as theabove-described low frequency signal.

In a retail store, for example, the data module 11 and/or the alarmmodule 13 (and/or a remote component of the system, such as a remoteserver described below in connection with FIG. 3) may be programmed tomonitor status data transmitted in the system 10 and/or to determinestatistical data corresponding to the product device 14. For example,the data module 11 may be programmed to log an evaluation of the productdevice 14. As shown in FIG. 1, the product 14 may be displayed in astatic, e.g., docked, position on the display 16, such as on the cradle18. As shown in FIG. 2, the processor of the security sensor device 12may be programmed to detect a consumer lifting the product 14 from thedisplay 16 and/or the cradle 18. Once the lift is detected, the securitysensor device 12 may be programmed to transmit status data indicative ofthe lift. The manner in which the lift is detected may vary. Forinstance, in some cases, the security sensor device 12 includes anaccelerometer configured to provide motion data used for lift detection.

A variety of statistical data may be captured, determined, logged,and/or otherwise acquired by the system 10. For instance, the timing,duration, type, and other characteristics of each product interactionmay be logged. Still further data may be acquired, including, thequantity and frequency of interactions with respective product devices,types of product devices, product displays, display locations, and othercategories or groups of product devices. Still other types of data maybe acquired, including, for instance, data other than product lifts. Forexample, data indicative of, or otherwise related to, alarm conditionsand/or usage (such as use of a key to disable or enable alarms),security sensor device health (e.g., battery information), alarm health(e.g., battery information), product status (e.g., charging or notcharging, charge rate, etc.) may be acquired.

With reference to the example of FIG. 2, components of the system 10include respective tags (e.g., identification tags) to facilitate theacquisition of the above-referenced data and other information regardingthe product devices 14, the product displays, and other aspects of thesystem 10. In this example, the security sensor device 12 and theproduct display 16 include tags 30, 32, respectively. Additional, fewer,or alternative components may include tags in other cases. For instance,as described below, one or more of the product devices 14 may includerespective tags. Each tag 30, 32 may be configured to uniquely identifya particular instance of the security sensor device 12, the productdisplay 16, etc. Thus, each security sensor device 12 may have a uniquetag for respective identification.

In some cases, each tag 30, 32 includes a label with a visualidentification code or other computer-readable marking. In the exampleof FIG. 2, the visual identification code is a unique quick response(QR) code. The label of each tag 30, 32 may be affixed to the securitysensor device 12. For example, the tag 30 for the security sensor deviceis a label affixed to an underside surface of the security sensor device12.

As described below, the tags 30, 32 may be read or scanned to pair,correlate, or otherwise associate particular instances of the securitysensor devices 12, product displays 16, and other components of thesystem 10 with one another. Such association of system components isgenerally referred to herein as registration. In one example, one of thesecurity sensor devices 12 may be registered with a particular productdevice by scanning the tag 30. The product device 14 may be identifiedby various techniques, including, for instance, scanning a tag, asdescribed below. The registration of two such items may be considered apairing. In other examples, more than two items are registered with oneanother. For instance, one of the security devices 12 may be registeredwith a particular product device 14 and a particular location, e.g.,display platform 16. The sensor-product and other associations may thenbe used to augment the data regarding the product interactions. Forexample, the interaction data for a particular security sensor device 12may then be associated with a particular type of product device, productdisplay, display location, etc. The registration data may be uploaded orotherwise provided to a database in which other data, e.g., interactiondata, is stored. Various users may then access the database via, e.g.,networked communications, to view, process, and otherwise use the data.Use scenarios are not limited to those involving the interaction data.For instance, the registration data may be useful in connection withfacilitating the proper installation or setup of product displays in theretail environment.

FIG. 3 depicts a system 300 for product display registration inaccordance with one example. In this case, the system 300 includes threeinstances of product display apparatus 302-304. Each product displayapparatus 302-304 is configured to support one or more product devices306-308 on display. Only a single product device is shown with eachproduct display apparatus for ease in illustration. In some cases, eachproduct display apparatus 302-304 includes a display platform, such asthe display platform 16 of FIGS. 1 and 2. The product display apparatus302-304 may alternatively or additionally include other structures. Forexample, the product display apparatus 302-304 may include a post orother extension on which a product device is mounted or otherwisedisposed. The configuration of the product display apparatus 302-304 andthe arrangement of the product devices 306-308 may vary considerably.The manner in which the product display apparatus 302-304 supports theproduct devices on display may thus vary.

Each product device 306-308 is protected by a respective security sensordevice 310-312. In some cases, each security sensor device 310-312 isconfigured for wireless communications with an alarm unit 314 or othercontrol unit of the system 300. The wireless communications may beimplemented as described above. Each security sensor device 310-312 maybe otherwise configured as described above in connection with theexamples of FIGS. 1 and 2. The configuration of the security sensordevices 310-312 may vary. For instance, one or more of the securitysensor devices 310-312 may include functionality other than securitysensing, as described below.

Components of the system 300 include a marking or other tag 316 toidentify the components for registration. Each tag 316 may becomputer-readable or otherwise capable of being processed to obtainidentification data for the component of the system 300. In some cases,the tag 316 is or includes a computer-readable marking, such as a QRcode as described above in connection with FIG. 2. A variety of othervisual identifiers may be used, including, for instance, bar codes. Thecomputer-readable marking may or may not involve affixing a label to thesystem component. For example, the marking may be displaying on a screenof the system component (e.g., product device) or provided in some otherway, such as via a catalog. For example, the product device 306 may beconfigured to generate an image of the tag 316 on a user interface ofthe product device 306. In other cases, the tag 316 is or includes acircuit configured for wireless communication of the identificationdata, such as an RFID tag. The circuit may be passive or active.

In still other cases, the tag 316 may be audible, as in a beep or othersound generated by the component of the system 300. For instance, thesecurity sensor device 310-312 is configured to emit sound indicative ofthe sensor identification data. The emitted sound may then be capturedvia, e.g., a microphone or other audio scanning. To this end, thesecurity sensor devices may be configured for bi-directional audiocommunications, e.g., for providing and/or obtaining identificationdata. The nature and other characteristics of the tags 316 may thusvary.

The nature of the identification data provided by the tags 316 variesbased on the item being identified. The identification data for theproduct devices 306-308 is referred to herein as product identificationdata, and may be indicative of the product device. For instance, theproduct identification data may be indicative of a particular type(e.g., manufacturer, model, model name, etc.) of product device and/or aparticular instance of the product device (e.g., a serial number,International Mobile Equipment Identity (IMEI) number, or other identitynumber). The identification data for the security sensor devices 310-312is referred to herein as sensor identification data, and may beindicative of one of the security sensor devices (e.g., a particularinstance of the security sensor devices). The identification data forthe product display apparatus 302-304 may be or include display locationdata indicative of a location of the product display apparatus. Forinstance, the display location data may be indicative of a platform,table, cradle, base, cord winder, area, or other portion of the displayapparatus or retail environment in which the product display apparatusis located. Thus, in some cases, the display location data may beindicative of objects that are capable of being moved about the retailenvironment. Alternatively or additionally, the display location data isindicative of a physical, fixed location in the retail environment, suchas a fixture of the retail environment and/or display apparatus.

The system 300 presents multiple techniques for acquiring or otherwiseobtaining the identification data from the tags 316. One technique usesa scanner 318 of the system 300 to acquire the identification data. Inthis technique, the scanner 318 is an independent device (e.g.,independent of the other components of the system 300) that, in somecases, is dedicated to acquiring the identification data. In the exampleof FIG. 3, the scanner 318 is configured to read or otherwise obtain theidentification data from the product display 302, the security sensordevice 310, and the product device 306 by scanning or reading the tags316 thereof. In cases in which the tags 316 are markings, the scanner318 may thus be or include a camera or other image acquisition device toobtain an image of the tags 316. The scanner 318 may then process thecaptured images to determine or otherwise obtain the identification datafrom the tags 316. For instance, the scanner 318 may be configured toread the tag 316 of the security sensor device 310 to capture or obtainthe sensor identification data for that particular item. Similarly, thescanner 318 may be configured to read the tag 316 of the product device306 to capture or obtain the product identification data for thatparticular item. Lastly, the scanner 318 may be configured to read thetag 316 of the product display apparatus 302 to capture or obtain thedisplay location data for that particular display location.

Some techniques for obtaining the identification data from the tags 316utilize one of the other components of the system 300 to acquire theidentification data. In such cases, the component providing the scanningfunction may itself be one of the devices or items being registered. Thescanner may be a built-in component of the device. The scanner 318 isthus integrated with the system 300, rather than an independent orstandalone component thereof. In the example of FIG. 3, one of theproduct devices 308 includes a scanner 320 or reader configured toacquire the identification data. In one example, the product device 308is a phone or other handheld device with a camera. To acquire theidentification data, the camera captures images of the tags 316 of theproduct display apparatus 304 and the security sensor device 312 asshown schematically in FIG. 3. In some cases, the product device 308 maybe configured to operate in a manner similar to the standalone scanner318.

In yet another technique, one of the security sensor devices 311includes a scanner 322 or reader. The example of FIG. 3 depicts twodifferent data acquisition techniques. In one case, the scanner 322obtains image data via a camera or other image acquisition device.Alternatively or additionally, the scanner 322 is configured toestablish wireless communications 324 with the tags 316 to obtain theidentification data. The wireless communications may be RFIDcommunications, near field communications (NFC), and/or other radiofrequency communications. As described above in connection with FIGS. 1and 2, the security sensor device 311 may be further configured tocollect interaction data for the product device 307. The interactiondata is indicative of consumer interaction with the product device 307.

In cases having integrated scanning, the identification data for thedevice having the scanner may be obtained without scanning or reading atag. For example, the device having the integrated scanner may obtainits own identification data by accessing a memory of the device.Obtaining the identification data may thus, in some cases, include adata lookup, memory access, or other data acquisition procedure. Memoryaccess or other procedures may be useful, for example, in obtaining theIMEI or serial number of a product device. Alternative or additionaltechniques for obtaining identification data without scanning includeusing a wired connection between the source and destination of theidentification data. For example, if a security sensor device isgathering or otherwise obtaining identification data, the displaylocation data may be provided to the security sensor device via a cableor other wired connection between the product display apparatus and thesecurity sensor device. Alternatively or additionally, theidentification data may be communicated or provided or obtained througha power connection, e.g., using power line communications. To that end,the system 300 may include a power hub that modulates, encodes, and/orotherwise transmits messages via the power line connected to, forinstance, each cradle, base, or other display apparatus.

In many cases, not all of the techniques are utilized in a particularimplementation of the system 300. For instance, the independentscanner-based technique may not be utilized in examples in which all ofthe product devices on display in a particular retail environment arecapable of acquiring identification data. Multiple techniques arenonetheless shown together in the example of FIG. 3 for ease inillustration. Additional, fewer, or alternative techniques may thus beprovided. For instance, one alternative technique involves using one ofthe product devices 308 to acquire identification data for itself aswell as other product devices 306, 307. The product device 308 may thusact as a scanner for the other product devices 306, 307.

The identification data may be obtained in still other ways. Techniquesother than those shown in FIG. 3 may be used to obtain theidentification data. For instance, in some cases, the product device 308may be configured for NFC, RFID, and/or other wireless communications toobtain the identification data. Other types of electronic tags may beused. Other techniques may include or involve user entry of data into auser interface of one of the components of the system 300, such as oneof the security sensor devices and/or one of the product devices. Theuser interface may be or include a web page, a spreadsheet, document, orother dialog for data entry.

The system 300 generates registration data based on the identificationdata. For example, the registration data to associate or register one ofthe security sensor devices and one of the product devices is based onthe respective sensor identification data and the respective productidentification data. The registration data thereby associates therespective security sensor device and the product device with oneanother. In the example of FIG. 3, the registration data for the productdisplay apparatus 302, the security sensor device 310, and the productdevice 306 is based on the identification data obtained via the scanner318.

The system 300 includes one or more processors 330, 332 configured togenerate registration data based on the identification data. In theexample of FIG. 3, one of the processors 330 is a microprocessor of thescanner 318. The other processor 332 is a microprocessor of the alarmunit 314. Other types of processors may be used. For instance, theprocessor may be or include a microcontroller or other controller.Additional, fewer, or alternative processors may be provided. Forexample, one of the product devices, such as the product device 308 withthe scanner 320, may also include a processor configured to generate theregistration data.

The manner in which the registration data is generated from theidentification data may vary. In some cases, the registration data mayinclude the identification data. For example, the registration data maybe or include a concatenation or other combination of the identificationdata for the associated security sensor device, product device, and/orproduct display apparatus. Alternatively, the registration data mayinclude a subset of the identification data. For example, generating theregistration data may involve removing one or more portions of theidentification data not necessary for identifying the items. Theregistration data may be generated by translating the identificationdata into a different format. For example, a QR code or otheridentification data may be applied to a lookup table, key, or otherfunction to generate a portion of the registration data. Theregistration data may be derived from the identification data in stillother ways. For example, the registration data may be generated by ahash or other function that takes the identification data as inputparameters.

The system 300 includes a gateway 340 to support network communications.The network communications send the registration data to a networkstorage device. The communications may be between components of thesystem 300 and/or with elements outside of the system 300. In theexample of FIG. 3, the gateway 340 supports communications between thealarm unit 314 and a server computer 350. The server computer 350 may beor include a remote computer, e.g., remote from the retail environmentin which the product devices 306-308 are on display. The communicationswith the server computer 350 may thus include or involve an internetconnection. The communications may accordingly use internet protocol(IP), in which case the gateway 340 is configured as an IP gateway. Theserver computer 350 may or may not be a component of the system 300.Other protocols or types of communications may be used.

The gateway 340 may be or include a modem, router, and/or othercommunication devices. Alternatively, the gateway 340 includes a servercomputer or other computer. The configuration and other characteristicsof the gateway 340 may vary. For example, in some cases, the gateway 340includes a set of connected devices, such as a modem, router, and servercomputer.

The system 300 may use additional or alternative network communications.For example, the product device 308 may send identification data and/orregistration data to the server computer 350 directly (e.g., without thealarm unit 314 as an intermediary). As shown in FIG. 3, a communicationlink may be established between the scanner 320 of the product device308 and the server computer 350. Thus, in some cases, the product device308 includes a network communication device for sending the registrationdata to a network storage device, such as the server computer 350. Instill other cases, the network communication device is provided byanother component of the system 300, such as one of the security sensordevices 311

Storage on the server computer 350 or other network storage device makesthe registration data accessible for various uses. For example,registration data and the associated interaction data may be aggregated,compared, or otherwise processed for multiple retail sites. The servercomputer 350 may include a database manager 352 configured to receiveand respond to database queries and implement other processingoperations on a database 354 in which the registration and other data isstored. The registration data may be used for additional or alternativepurposes. For example, the registration data may be accessed inconnection with disabling or locking an instance of a product devicethat enters an alarm status while on display. In such cases, the IMEIand/or serial number may be used to disable or lock the product device.To that end, the server computer 350 may generate and send a message tothe product device (and/or another server associated with the productdevice).

The registration data sent to the server computer 350 may be furtherprocessed by the server computer 350. For example, the registration datamay be reformatted or otherwise transformed before storage in thedatabase 354. Thus, the registration data stored in, and accessiblefrom, the server computer 350 may differ from the registration data sentvia the IP gateway 340 or other network communication device.

FIG. 4 is a flow diagram of a method 400 of registering a securitysensor device with a product device to be protected via the securitysensor device. The method 400 may be implemented by one of theprocessors 330, 332 described above in connection with the system 300 ofFIG. 3, or another processor, such as a processor of the security sensordevice 311 (FIG. 3) or the product device 308 (FIG. 3). Alternatively,the method 400 is implemented by more than one of the above-describedprocessors. For example, some of the acts of the method 400 may beimplemented by the processor 330 (FIG. 3) and/or other processor of adevice that scans or otherwise obtains identification data, while one ormore other acts are implemented by the processor 332 (FIG. 3). In stillother cases, one or more acts of the method 400 are implemented by aprocessor other than those shown or described in connection with theexamples of FIG. 3.

The method 400 includes an act 402 in which sensor identification datais obtained for the security sensor device. The sensor identificationdata is indicative of the security sensor device. For example, thesensor identification may be indicative of an instance of the securitysensor device. Each instance may be uniquely identified by a serialnumber or other distinct unit number or other code. The nature of thesensor identification data may thus vary.

The security sensor device may be one of the security sensor devicesdescribed hereinabove. The sensor identification data may be receivedfrom different sources, captured via various types of readers or otherscanners, derived from raw data acquired by the various types ofscanners, or otherwise captured, acquired, or determined. In some cases,the security sensor device obtains the sensor identification data fromitself. The manner in which the sensor identification is obtained in theact 402 may thus vary. Further details are provided below in connectionwith a number of examples.

Product identification data is obtained in an act 404 for the productdevice protected by the security sensor device for which sensoridentification data is obtained. The product device and the securitysensor device may thus be associated or registered with one another. Theproduct identification data may be indicative of the product device inone or more ways. For instance, the product identification data may beindicative of a product name and/or product model. Alternatively oradditionally, the product identification data may be indicative of aserial number, IMEI number, and/or other data indicative of a particularinstance of the product device. The nature of the product identificationdata may thus vary. The product device may be any one of the productdevices described in connection with the examples of FIGS. 1-3.

The manner in which the product identification data is obtained in theact 404 may vary. The product identification data may be received fromdifferent sources, captured via various types of readers or otherscanners, derived from raw data acquired by the various types ofscanners, or otherwise captured, acquired, or determined. In some cases,the product device obtains the product identification data from itself.Further details are provided below in connection with a number ofexamples.

The method 400 includes an act 406 in which registration data isgenerated for the security sensor device and the product device. Theregistration data is generated based on the sensor identification dataand the product identification data. The registration data associatesthe security sensor device and the product device with one another. Theregistration data may be generated by one of the above-describedprocessors or a different processor. The generation of the registrationdata may occur in connection with the transmission of the registrationdata to, for instance, a remote storage device. The timing of thegeneration may nonetheless vary. For instance, the registration data maybe generated after data transmission of the identification data (and/orraw or other data underlying the identification data). The nature of theregistration data may also vary, as described herein.

The act 406 may include other processing of the registration data. Forexample, in some cases, the registration data is processed with otherdata, such as activity data indicative of activity involving the productdevice and/or the security sensor device. For instance, the activitydata may be indicative of consumer interaction with the product deviceand/or indicative of alarm or other status data provided by the securitysensor device.

FIG. 3 depicts a number of options and examples of the acts 402, 404,406, and 408. Each act is addressed separately below.

The sensor identification data may be obtained in the act 402 in avariety of different ways. In some cases, one or more codes, such as QRor other labels or other visual markings, for the sensor identificationdata are captured or otherwise obtained in an act 410. The code(s) maybe raw data from which the sensor identification data is derived, and/orconstitute the sensor identification data itself. The code(s) may becaptured or acquired via scanning (e.g., optical, RFID, or otherscanning) the security sensor device, and/or wireless communications(e.g., NFC communications) with the security sensor device. Varioustypes of scanners may be used, as described above. Obtaining the sensoridentification data may thus include establishing a wirelesscommunication link with the security sensor device, such as a linkbetween a scanner and the security sensor device. In some cases, theproduct device is configured to implement, or otherwise includes, thescanner. The wireless communication link may involve both the securitysensor device and the product device in these and other cases.

Alternatively or additionally, the code(s) are obtained via memoryaccess. For instance, the code(s) may be accessed in the memory of thesecurity sensor device. The memory access may be useful in cases inwhich the security sensor device is configured to provide, or otherwiseinclude, a scanner, e.g., for obtaining other types of identificationdata. In cases in which a separate, independent, or other scanner isused, code(s) underlying or otherwise for the sensor identification datamay be received from the scanner in an act 412. In these and othercases, obtaining the sensor identification data may include deriving orotherwise determining in an act 414 the sensor identification data fromthe code(s).

The act 402 may also include verifying a security sensor device in anact 416. Verification may be useful in one or more ways. For example,the security sensor device may be verified as an eligible device.Security sensor devices deemed eligible for registration with theproduct device may correspond with those deemed well-suited forprotecting the product device. The manner in which the security sensordevice is verified may vary. For instance, the verification process mayinclude checking the code(s) or sensor identification data against adatabase of security sensor devices. In other examples, the scanner maybe capable of implementing the verification.

Obtaining the product identification data in the act 404 may includecapturing or otherwise obtaining one or more codes via scanning,wireless communications, memory access, or other acquisition techniquesin an act 418. The scanning and wireless communications techniques maybe similar to those described above. Various types of scanners may beused, including built-in or integrated scanners, as well as separate orindependent scanners. A memory access may be used to obtain the code(s)for the product identification data when the product device isconfigured to provide, or otherwise include, a scanner.

Alternatively or additionally, the code(s) for the productidentification data may be received in an act 420 via a user interfaceof the product device. For example, a scanner may provide a userinterface, such as a drop-down menu, that allows a user to select themodel, name, and/or other characteristic or identifier of the productdevice from a list. In some cases, the scanner is provided by theproduct device. Obtaining the product identification data may thusinclude receiving a user selection of the model (or other productcharacteristic) via the user interface.

The act 404 may include receiving the code(s) for the productidentification data from a scanner in an act 422. In some cases, thesecurity sensor device includes the scanner. A variety of scanners maybe used.

The code(s) may or may not constitute the product identification data.In some cases, the product identification data is derived or otherwisedetermined from the code(s) in an act 424. For example, a QR or othercomputer-readable code is translated into the product identificationdata by the scanner and/or other system component in communicationtherewith.

In the example of FIG. 4, the registration data further associates thesecurity sensor device and the product device with display locationdata. The display location data may be indicative of a location of aproduct display, such as the location of a display platform or cradle orother area in which the product device is displayed. The displaylocation data may be obtained in the act 406 in ways similar to thosedescribed above in connection with the sensor identification data andthe product identification data. For instance, as shown in the examplesof FIG. 4, the act 406 may include capturing one or more codes viascanning or wireless communications in an act 426. The code(s) mayalternatively be received in an act 428 via a user interface (e.g., viauser selection from a drop-down or other list). Obtaining the displaylocation data may also or alternatively include receiving in an act 430the code(s) from a scanner or other system component, such as thesecurity sensor device.

The processing of the registration data in the act 408 may includecompiling the identification data in an act 432. The identification datahad been obtained from a scanner, sensor, and/or other device, asdescribed above. The compiled identification data may then be forwardedor otherwise transmitted. In some cases, the registration data is sentin an act 434 to a network storage device for storage of theregistration data in a registration database. The act 434 may includesending the registration data within a networked computing architecture,such as via an alarm unit and an IP gateway as described above.Alternatively or additionally, the registration data may be sent from ascanner, such as a product device including the scanner.

The processing of the registration data may include various types ofdata analysis. In the example of FIG. 4, the registration data isanalyzed for location or other compliance in an act 436. The properplacement of the product devices may thus be confirmed. Other types ofcompliance checks may be implemented. For instance, the registrationdata may be analyzed to confirm that product devices are notout-of-stock or close thereto.

The processing of the registration data may also include sending,receiving, and/or storing other types of data in conjunction with theregistration data in an act 438. For example, activity data may bereceived from the security sensor device. The activity data may beindicative of activity detected by the security sensor device. In somecases, the activity data is indicative of consumer interaction with theproduct device. Other types of activities involving the product devicemay also be tracked via the activity data, including, for instance,alarm and other status data. The act 438 may then include storing theactivity data in a database in which the registration data is stored toassociate the activity data with the product device.

The order of the acts of the method 400 may differ from the exampleshown in FIG. 4. For instance, the product identification data may beobtained before or concurrently with the sensor identification data.

The method 400 may be implemented automatically and/or initiated by auser. For example, the method 400 may be implemented periodically orautomatically upon the occurrence a trigger event. Alternatively oradditionally, the implementation may be scheduled to coincide withvarious activities in the retail environment, such as display setup,display location compliance checks, or stock evaluations.

The method 400 may include additional, fewer, or alternative acts. Forinstance, the method 400 may include an act in which the identificationdata for a product device or other system component is changed. In oneexample, a product device updates its own identification information toa new name and/or number upon scanning or other reading. For instance, atemporary name is assigned whenever the product device is placed upon anNFC tag or reader, and/or a product display cradle or base. The name maythen be changed back, e.g., to a default name, upon removal from thatlocation.

Described above are systems and methods for the pairing, association, orother registration of product devices (or merchandise) and securitysensor devices protecting the merchandise. The registration may furtherinclude associating a particular product display apparatus or locationwith a respective product device. The pairing or other registration maybe facilitated through scanning or otherwise obtaining identificationinformation, such as optically, by radio frequency, or by audiofrequency, manually or automatically. In some cases, a separate mobilescanner may be used. In other cases, a scanner built-in to the securitysensor device itself and/or the product device itself is used. Forexample, the product device or other scanner may be configured to scanQR code or other labels fixed to the security sensor device and/or theproduct display apparatus, e.g., the display platform or base. QR orother codes may also be captured by scanning the code(s) displayed on adevice screen or printed as part of a product catalog. In other cases,NFC, RFID, or other wireless communications are used to obtain theidentification information. In still other cases, audio tones may beused to provide the identification information. The scanner or othersystem component may then forward registration data indicative of thesensor identification data, the product display location, and theproduct model information to a networked storage device.

Described below are systems and methods for automatically implementingsuch registration, e.g., registering security sensor devices withproduct devices protected thereby. The systems and methods automaticallypair or associate a respective one of the security sensor devices with arespective one of the product devices. The registration may alsoassociate the security sensor device and the product device with adisplay location, e.g., a display or plan-o-gram location and/or a sitelocation. Registration data indicative of the association orregistration may then be stored for networked access and use, asdiscussed above. Such automatic pairing or registration avoids errorsthat may arise from reliance on manual processes, such as QR codescanning. Automatic registration also avoids inaccuracies arising fromstore personnel manually entering incorrect information or neglecting toimplement the registration. The disclosed systems and methods may alsobe capable of un-registering security sensor devices and productdevices.

The automatic registration is based on timestamps (or timestamp data).The timestamps is indicative of the timing of events involving theproduct device (or merchandise) and the security sensor deviceprotecting the merchandise. The events are or involve an alteration inpower delivery to the merchandise and the security sensor device.

The timestamps (or timestamp data) are compared to one another. If twotimestamps match, then the corresponding security sensor device andproduct device are automatically linked or paired with one another.Registration data based on the comparison is accordingly generated. Theregistration data may be or include data similar to the registrationdata described above, including, for instance, a unique sensoridentifier for the security sensor device, and brand name, model number,unique serial number, IMEI, and other product specific information. Anetworked computing device, such as a server device, may obtain thetimestamps, implement the comparison, and generate the registrationdata.

The automatic registration may also support the automatic collection ofposition data. The position data may be or include display location dataand/or site location data. For instance, the position data may beindicative of a retail site and/or a plan-o-gram position within aretail site, as described above. For instance, a unique identifier of adisplay cradle may be automatically registered with the security sensordevice and the product device. The position data may be obtained invarious ways, e.g., in conjunction with data for the security sensordevice or independently thereof. For instance, the display location dataor other position data may be provided by the security sensor device,e.g., as part of a sensor identification data package. Alternatively oradditionally, the display location data or other position data may beobtained via a separate data package. One or more of the data packagesmay be sent via an IP gateway by which timestamp data for the securitysensor device is sent to the networked computing device.

FIG. 5 depicts a system 500 for product display registration usingtimestamps in accordance with one example. The system 500 is used inconjunction with the display of a product device 502. The product device502 may be merchandise on display in, e.g., a retail environment, asdescribed above. In some cases, some of the elements or components ofthe system 500 are disposed on-site (e.g., at the retail site), whileother elements or components of the system 500 are disposed remotely(e.g., the location of a server computer or other networked computingdevice).

The product device 502 and other aspects of the display may be similarto that described above in connection with the examples of FIGS. 1-3.For instance, the product device 502 may be an electronic device, suchas a phone, tablet, or other portable computing device. The productdevice 502 may be configured for wireless and/or other networkcommunications. The communications may be configured in accordance withinternet protocol (IP). Other communication protocols or types ofcommunications may be used. For instance, communications in accordancewith one of the IEEE 802.11 standards may be used. Alternatively oradditionally, the network communications to/from the product device 502are or include wired communications.

The system 500 includes an alarm control unit 504 to support orotherwise provide security-related services for the product device 502.The alarm control unit 504 may be configured similarly to the examplesdescribed above. For instance, the alarm control unit 504 may receivestatus updates and other data from the security sensor device(s) 512 todetermine whether to generate an alarm. The communications with thealarm control unit 504 may be wireless communications. For example, thealarm control unit 504 may communicate with other system components viaone of the IEEE 802.11 standards. The protocol and other characteristicsof the communications may vary. For instance, wired communications maybe used.

The system 500 includes a gateway 506 to support network communications.The gateway 506 may be configured similarly to the examples describedabove. For instance, the communications may use internet protocol (IP),in which case the gateway 506 is configured as an IP gateway. Otherprotocols or types of communications may be used, as described above.The gateway 506 may be or include a modem, router, and/or anothercommunication device. Alternatively, the gateway 506 includes a servercomputer or other computer. The configuration and other characteristicsof the gateway 506 may vary. For example, in some cases, the gateway 506includes a set of connected devices, such as a modem, router, and servercomputer.

The gateway 506 establishes or otherwise supports communications betweencomponents of the system 500 at the product display site and one or moreremote sites. In the example of FIG. 5, the gateway supportscommunications with a server computer 508 of the system 500. The servercomputer 508 may thus be located remotely from the product device 502and the alarm control unit 504. The server computer 508 is directed tosupporting the product display registration, as described below. In somecases, the server computer 508 provides registration-related servicesfor multiple alarm control units and product display sites. The servercomputer 508 may be or include one or more networked computing devices,the configuration of which may vary.

The system 500 includes a server device 508, e.g., server computerdevice, to implement one or more aspects of the registration. The serverdevice 508 may correspond with, or be configured similarly to, theserver or other networked devices described above, such as the server350 of FIG. 3. The server device 508 may receive data regarding theregistration via the gateway 506 or through other communications (e.g.,network communications). In the example shown, the server device 508receives data from the alarm control unit 504 through the gateway 506.The server device 508 may receive other data, such as data from theproduct device 502, via an IP or other communication link. Thecommunication link(s) allow the server device 508 to be or include aremote computer, e.g., remote from the retail environment in which theproduct device 502 is on display. The manner in which the server device508 communicates with the other components of the system 500 may thusvary. For instance, a variety of other protocols or types ofcommunications may be used.

The product device 502 is presented via a product display (or productdisplay apparatus) 510 of the system 500. The product display apparatus510 may be configured as described above in connection with the examplesof FIGS. 1 and 2. For instance, the product display apparatus 510 maycorrespond with, or include, the display platform 16 of FIGS. 1 and 2.The product display apparatus 510 may alternatively or additionallyinclude one or more other structures, as described herein.

The system 500 includes a security sensor device 512 to protect theproduct device 502 as described above. The security sensor device 512may be configured similarly to the examples described above. Forinstance, the security sensor device 512 may be or include a unitphysically attached, or otherwise secured, to the product device 502, asdescribed above. In the example shown, the security sensor device 512 isconfigured for wireless communications with the alarm unit 504 tosupport the generation of alarms or alerts, as described above.

In the example of FIG. 5, the security sensor device 512 is alsoconnected to the product device 502 via a port 514 of the securitysensor device 512. In some cases, the port 514 may be directed toproviding power and/or data to the product device 502 via, e.g., a port518 of the product device 502. In the example shown, the system 500includes a cable 518 for a wired connection between the ports 514, 516.The port 514 may be or include a socket or other terminal. Other typesof interfaces may be used.

The security sensor device 512 may receive power via the product displayapparatus 510. In the example of FIG. 5, the product display apparatus510 includes a cradle 520. The cradle 520 is configured to support theproduct device 502 and the security sensor device 512. As describedabove, the security sensor device 512 may engage the cradle 520 toposition the product device 502 on the product display apparatus 510. Inthe example shown, the cradle 520 includes power pins 522 positioned andotherwise configured to engage or contact power pins 523 of the securitysensor device 512. Placement of the security sensor device 512 on thecradle 520 aligns the power pins 522, 523 as shown. In some cases, thealignment of the power pins 522, 523 establishes contacts for currentflow to the security sensor device 512.

The manner in which power is delivered to the security sensor device 512and the product device 502 may differ from the example shown. Forinstance, the product display apparatus 510 and the security sensordevice 512 may not have power pins. Power may instead be providedwirelessly, e.g., via an inductive connection between the productdisplay apparatus 510 and the security sensor device 512. A wireless(e.g., inductive) connection may also be established between thesecurity sensor device 512 and the product device 502. Power mayalternatively or additionally be delivered capacitively.

Events in the delivery of power to the security sensor device 512 andthe product device 502 are used to support the registration. Powerevents involve an alteration in the delivery of power. Power events mayinvolve a power connection (i.e., power being supplied) or a powerdisconnection (i.e., power not being supplied). The timing of each powerevent is identified, e.g., via a timestamp. Sensor timestamps identifythe timing for alterations in power delivery to security sensor devices512. Product timestamps identify the timing for alterations in powerdelivery to product devices 502. The sensor timestamps and producttimestamps from various security sensor devices 512 and product devices502 are then compared, e.g., by the server device 508, as describedbelow. A particular security sensor device 512 is paired or registeredwith a particular product device 502 based on the comparison, e.g., whenthe respective timestamps match.

In the example of FIG. 5, power events occur when the product device 502and the security sensor device 512 are lifted from or placed on thecradle 520. When lifted from the cradle 520, the security sensor device512 no longer receives power via the power pins 522, 523. As a result,the power port 516 of the product device 502 no longer receives powervia the cable 518. The respective timing of each power disconnection isthus the same (e.g., roughly the same). The respective timestamps willthus match. When placed on the cradle 520, the security sensor device512 receives power via the power pins 522, 523. As a result, the productdevice 502 receives power via the power port 516 and the cable 518. Therespective timing of each power connection is thus the same (e.g.,roughly the same), and the timestamps will again match.

Timestamped data for each power event is provided to the server device508 to associate, or register, a respective product device 502 with arespective security sensor device 512. For example, the timestamped datamay be sent as a data package. The data package includes dataidentifying the device and the timestamp data. In the example shown, theidentification data is or includes either sensor identification data orproduct identification data. Additional data may be included, including,for instance, position data regarding a display location or site of thedevice. The components, configuration, and other aspects of thetimestamped data may vary from the example described above.

The security sensor device 512 is configured to generate and provide thetimestamped data for each power event. In the example shown, thesecurity sensor device 512 includes a microcontroller 524 and a memory526. The microcontroller 524 may be or include one or more processors.The memory 526 may be or include one or more memories. The sensoridentification data may be stored in the memory 526 and accessed by themicrocontroller 524 to generate the timestamped data. Themicrocontroller 524 may be configured by instructions stored in thememory 526 or another memory, such as an internal memory. In the exampleof FIG. 5, when the power event occurs, the microcontroller 524wirelessly communicates the sensor identification data stored in thememory 526 of the security sensor device 512 to the alarm control unit504. A microprocessor 528 of the alarm control unit 504 then sends thedata, including the sensor timestamp and the sensor power eventinformation, to the server device 508 through the gateway 506.

The product device 502 is also configured to generate and provide thetimestamped data for each power event. In the example shown, the productdevice 502 includes one or more processors 530 and one or more memories532. The processor 530 may be configured to execute a service,application, or other procedure in accordance with instructions 534stored in the memory 532. For instance, the instructions 534 may causethe processor 530 to monitor the power port 516 of the product device502. When the power event occurs, execution of the instructions 534causes the processor 530 to generate and send the timestamped data tothe server device 508.

The product device 502 may send the timestamped data to the serverdevice 508 via a different route than the security sensor device 512.For instance, the product device 502 may send the product timestampeddata via a wireless local area network and/or cellular networkcommunication link, rather than via the alarm control unit 504.

One or both of the data packages may include plan-o-gram or otherposition data. For example, the sensor data package may further includea unique cradle identifier for the cradle 520. In some cases, the cradle520 includes circuitry 536 that sends the unique cradle identifierthrough the power pins 522, 523 to the security sensor device 512 whenthe security sensor device 512 is sitting on the cradle 520. The cradleidentifier may be provided to the security sensor device 512 inadditional or alternative ways, including, for instance, via a separatewired or wireless connection. The unique cradle identifier may include aretail display position, a plan-o-gram position, and/or a storeidentifier. Additionally or alternatively, the sensor data package mayinclude a unique alarm control unit identifier. The unique alarm controlunit identifier may include a retail display position, a plan-o-gramposition, and/or the store identifier. Additionally or alternatively,the sensor data package may include a unique gateway identifier. Theunique gateway identifier may include the location of the gateway 506and/or the store identifier. The location of the gateway 506 may beobtained through cellular, GPS, and/or W-Fi network location services.

The manner in which the position data is added to one or both of thedata packages may vary. In some cases, the position data is added to thesensor data package by the security sensor device 512 when sending thesensor data package. Alternatively, the position data is added to thesensor data package by the alarm control unit 504 and/or the gateway 506after receiving the sensor data package from the security sensor device512.

The position data may be obtained by the server device 508 separately orindependently from the other identification data. For instance, positiondata for a respective security sensor device may be obtained via anidentification of the respective gateway 506. Each gateway 506, in turn,is associated with a respective site location. In some cases, eachgateway 506 sends its unique gateway identifier and data indicative ofthe security sensor devices 512 at its respective site locationseparately from other data packages. The site location and otherposition data may thus be obtained in ways in addition and/oralternative to the other data packages.

The server device 508 generates registration data based on thetimestamped data. The timestamped data is received independently fromthe product device 502 and the security sensor device 512. As describedabove, the registration data associates or registers the security sensordevice 512 and the product device 502. The server device 508 includesone or more processors 538 configured to generate the registration data.In this example, the server device 508 further includes database orother storage 540 in which the registration data is stored.

The server device further includes one or more memories 542. In theexample shown, correlation instructions 544 and database managementinstructions 546 are stored in the memory 542. Execution of thecorrelation instructions 544 causes the processor 538 to scan thereceived data stored in the database storage 540 for timestamp matches.If a match, or multiple matches are found, registration data associatingthe sensor identification data to the product identification data isautomatically generated by the processor 538. The registration datathereby associates the corresponding security sensor device 512 andproduct device 502 having the matching timestamps with one another.After the security sensor device 512 and the product device 502 areassociated, execution of database management instructions 546 cause theprocessor 538 to store the registration data in the storage 540.

If the timestamped data includes position data, the registration dataalso associates the cradle 520, the alarm control unit 504, the gateway506, or other positional data with the security sensor device 512 andthe product device 502.

FIG. 6 is a flow diagram of a method 600 of registering a securitysensor device with a product device to be protected via the securitysensor device. The method 600 may be implemented by one or moreprocessors, such as the processor 538 of the server device 508 (FIG. 5).Additional or alternative processors may implement the method 600.

The method 600 includes an act 602 in which sensor data (e.g., sensoridentification data) is obtained for the security sensor device. Thesensor data identifies the security sensor device and includes atimestamp for an alteration in power delivery to the security sensordevice. The alteration in power delivery to the security sensor deviceinvolves or includes a power connection or disconnection between thesecurity sensor device and a display location via which power isdelivered to the security sensor device.

The security sensor device may be one of the security sensor devicesdescribed hereinabove. The sensor data may be received from differentsources or otherwise captured, acquired, or determined. In some cases,the security sensor device obtains the sensor identification data from amemory of the security sensor device.

In the example of FIG. 6, position data for the sensor-productcombination is obtained in an act 603. The position data may beindicative of a display location, such as the location of a cradle,stand, base, or other display fixture, and/or a site location, such as aretail site. The position data may be or include plan-o-gram data, asdescribed above. The position data may be obtained via an IP gatewayand/or other devices at the site. In some cases, the position data maybe sent via a dedicated data package or other communication separate andindependent from other data packages. Additionally or alternatively, oneor more types of position data may be obtained in conjunction with theother identification data, such as the sensor data. For instance,plan-o-gram and/or other position data may be integrated with the sensoridentification data in a sensor data package.

Product data (e.g., product identification data) is obtained in an act604 for the product device protected by the security sensor device. Theproduct device and the security sensor device may thus be associated orregistered with one another. The product data identifies the productdevice and includes a product timestamp for an alteration in powerdelivery to the product device. The product data may identify theproduct device in one or more ways. For instance, the product data maybe indicative of a product name and/or product model. Alternatively oradditionally, the product data may be indicative of a serial number,IMEI number, and/or other data indicative of a particular instance ofthe product device. The product data may be received as a product datapackage including product identification data and product power eventdata. The product power event data is indicative of an alteration indelivery of power to the product device.

The manner in which the product identification data is obtained in theact 604 may vary. The product data may be received from differentsources or otherwise captured, acquired, or determined. In some cases,the product device obtains the product identification data from a memoryof the product device.

The method 600 includes an act 606 in which a comparison of the sensortimestamp and the product timestamp is implemented. The comparison maybe part of a procedure in which successive attempts to match timestampsare implemented. For example, a particular product timestamp may becompared with a plurality of sensor timestamps until a match is found ora predetermined amount of time has elapsed, e.g., since the timeindicated on the timestamp. Alternatively or additionally, a particularsensor timestamp may be compared with a plurality of product timestampsuntil a match is found or a predetermined amount of time has elapsed.

The method 600 includes an act 608 in which registration data isgenerated for the combination of the security sensor device and theproduct device. The registration data is generated based on thecomparison of the respective timestamps. For example, the registrationdata associates a security sensor device and a product device havingmatching timestamps. The registration data may also associate thedevices with position data, such as the location of the product displayand/or a site location.

The act 608 may include other processing of the registration data. Forexample, in some cases, the registration data is processed with otherdata, such as activity data indicative of activity involving the productdevice and/or the security sensor device. For instance, the activitydata may be indicative of consumer interaction with the product deviceand/or indicative of alarm or other status data provided by the securitysensor device.

FIG. 6 depicts a number of examples of the acts 602, 604, 606, and 608.Each act is addressed separately below.

The sensor data may be obtained in the act 602 in a variety of differentways in an act 610. In some cases, the sensor data is sent to the serverdevice for storage of the sensor data in a database. The act 610 mayinclude establishing a communication link for sending the sensor datawithin a networked computing architecture, such as via an alarm unitand/or an IP gateway as described above. The alarm unit and/or the IPgateway may be located at a site in which the product device is located.Alternatively or additionally, the sensor data may be sent from asecurity sensor device or a product device.

Alternatively or additionally, the sensor data in the act 602 may bereceived in a variety of different forms in an act 612. In some cases,the sensor data may be received as a sensor data packet that includessensor identification data and sensor power event data. The sensor datapacket may include additional data, such as position data, e.g., displaylocation data and/or site location data. The sensor power event data isindicative of whether the alteration in power delivery involves either astart or an end of power delivery to the security sensor device. Thedisplay location or other position data is indicative of a location of aproduct display in which the product device is displayed. For example,the position data may identify a cradle configured to receive thesecurity sensor device, and/or the display location identifies aplan-o-gram position of the location of the product display. Theplan-o-gram position is a physical position that defines where eachsensor and/or product are placed in the store. The site location isindicative of a site in which the product display is located.Alternatively or additionally, a store location is determined from thesensor data that includes site location data that is indicative of asite in which the product display is located, in an act 616.

The product data may be obtained in the act 604 in a variety ofdifferent ways in an act 618. In some cases, the product data is sent tothe server device for storage of the product data in the database. Theact 618 may include establishing network communication for sending theproduct data from the product device 502, as described above.

Alternatively or additionally, the product data in the act 602 may bereceived in a variety of different forms in an act 620 via a service orapplication executing on the product device. The product data may bereceived as a product data packet that includes product identificationdata and product power event data in an act 622. The product power eventdata is indicative of whether the alteration in power delivery involveseither a start or an end of power delivery to the product device.

The comparison of the sensor timestamp and the product timestamp may beimplemented in the act 606 in a variety of different ways. Theimplementing of the comparison may include determining whether thesensor timestamp and the product timestamp match in an act 624. Theimplementation of the comparison may include determining whether boththe sensor power event data and the product power event data matchregarding whether the alteration in power delivery involves either astart or an end of power delivery in an act 626. The comparison may beimplemented by the processor of the server device 508, as describedabove, via the execution of correlation instructions to determinewhether both the sensor power event data and the product power eventdata match. Additionally or alternatively, the comparison may becontinuously implemented until an exact match or a match within athreshold occurs in an act 628.

The generation of the registration data in the act 608 may includeassociating the sensor data and the product data if the comparisonreveals that the sensor timestamp and the product timestamp match orsufficiently match regarding whether the alteration in power deliveryinvolves either a start or an end of power delivery in an act 630.Additionally or alternatively, the registration data may associate thedisplay location data and/or the site location data with the securitysensor device and the product device. The respective data may beobtained as described above. The processor of the server device 508 mayexecute correlation instructions to generate the registration data asdescribed above.

The registration data may then be forwarded or otherwise transmitted. Insome cases, the registration data is sent in an act 632 to a storagedevice (e.g., a network storage device) for storage of the registrationdata in a registration database. The processor of the server device 508may execute database management instructions to store the registrationdata in the storage device as described above.

The generation of the registration data may also include sending,receiving, and/or storing other types of data in conjunction with theregistration data in an act 634. For example, activity data may bereceived from the security sensor device. The activity data may beindicative of activity detected by the security sensor device, such asthe amount of times the product device is picked up by a customer. Insome cases, the activity data is indicative of consumer interaction withthe product device, such as the amount of times the product device ispicked up by a customer. Other types of activities involving the productdevice may also be tracked via the activity data, including, forinstance, alarm and other status data. The act 634 may then includestoring the activity data in the database in which the registration datais stored to associate the activity data with the product device.

The order of the acts of the method 600 may differ from the exampleshown in FIG. 6. For instance, the position data and/or the productidentification data may be obtained before or concurrently with thesensor identification data.

The method 600 may include additional, fewer, or alternative acts. Forinstance, the method 600 may include an act in which the identificationdata for a product device or other system component is changed. In oneexample, a product device updates its own identification information toa new name and/or number upon scanning or other reading. For instance, atemporary name is assigned whenever the product device is placed upon anNFC tag or reader, and/or a product display cradle or base. The name maythen be changed back, e.g., to a default name, upon removal from thatlocation.

The above-described registration methods and systems may help to avoiduser error in recording the pairings and other associations in a retailenvironment. Further user error may be avoided in cases in which productdisplay location is part of the registration data. The registration datamay allow a user to determine if product positions have changed. Stillother uses of the registration data may be supported. For example,stock-out compliance may be supported by periodically obtaining theproduct display location information.

FIG. 7 depicts a method 700 for un-registration of security sensordevices and product devices. The method 700 may be implemented after asecurity sensor device and a product device have been associated withone another. The method 700 may provide an automatic way to un-pair orotherwise un-register the security sensor device and the product device.Security sensor devices and product devices may be disassociated orun-registered in additional or alternative ways, including, forinstance, manual and other adjustments to the data stored in or by anetwork storage device.

The method 700 may be implemented by one or more of the processorsdescribed herein. In some cases, the processor of an alarm control unitor other on-site device, such as an IP gateway, implements the method700. Alternatively, the processor of a server control device implementsthe method 700. In still other cases, a combination of processorsimplements the method 700.

In the example of FIG. 7, automated un-registration may begin withdetection of the detachment of the security sensor device and theproduct device in an act 702. For example, an alarm control unit maydetect the detachment. In some cases, the detachment may be detectedfirst by the sensor device itself, after which a message is sent by thesensor device to the alarm control unit. The detection may thus involvemore than one step or act, and may be indirect or direct. In othercases, additional or alternative trigger events may be detected in theact 702. For example, the disassociation of the security sensor deviceand the product device may be initiated by the selection of an option onthe product device and/or security sensor device.

Once the detachment or other event is detected, a timer is started in anact 704. The nature of the timer may vary. For instance, the timer maybe a count-up or count-down timer. The timer may or may not be trackingelapsed time. For instance, the timer may instead track a number ofcycles of a routine being implemented by the processor. Still othertimers or timing indications may be used.

In an act 706, the security sensor device and the product device areun-paired or otherwise un-registered once the timer exceeds a threshold.For example, the un-registration occurs when the timer exceeds apredetermined time limit, e.g., 30 seconds. Alternative or additionalconditions may be used. For example, the un-registration may bedependent upon exceeding the threshold while an alarm condition is notactive.

FIG. 7 depicts a number of optional acts for each act 702, 704, 706, ofthe un-registration method 700. The detection of the detachment mayinclude receiving or otherwise obtaining an indication of an alarm in anact 708. For example, a server device or alarm control unit may receivea message regarding an alarm condition. In this case, a store employeemay have detached the product device before remembering to deactivatethe alarm or otherwise disarm the security sensor device. Alternativelyor additionally, the act 702 includes or involves receiving or otherwiseobtaining in an act 710 a data package from the security sensor deviceregarding the detachment or other event warranting the un-registration.The detachment or other event may be detected in still other ways,including, for instance, detection of the power cable disconnectiondirectly in an act 712.

The un-registration of the act 706 may vary in several respects. Forinstance, the act 706 may or may not include sending one or moreinstructions to a server device in an act 714. The instruction(s) toun-register may be sent by the security sensor device, the alarm controlunit, and/or the IP gateway. Alternatively, the un-registration may bedirectly implemented in an act 716 in which, for instance, a database isadjusted. The un-registration may include or involve any number ofadditional or alternative acts, including, for instance, an updated listof active security sensor devices being sent or received in an act 718.The removal of a respective one of the security sensor devices from thelist may then be used by the server device or other processor toun-register any devices or positions from the respective sensor securitydevice.

The method 700 may include fewer, additional, or alternative acts. Forinstance, the method 700 may include one or more acts directed toattempting to pair or otherwise associate a detached security sensordevice with a different product device.

In some cases, one or more of the automated aspects of theabove-described registration methods and systems of FIGS. 5-7 may becombined with one or more of the manual aspects of the methods andsystems of FIGS. 1-4. For instance, in some cases, timestamps may stillbe used to associate or register sensor and product devices with oneanother, but a scanner, such as a scanner provided by the productdevice, may be used to gather identification data, such as productidentification data and/or position data. Such gathering may be usefulin preparing data to be sent to the server device. Manual and automatedregistration procedures may be integrated or combined in alternative oradditional ways. For example, the un-registration method 700 of FIG. 7may be supplemented by user-initiated or user-implemented requests forun-registration or disassociation made via one or more user interfacesprovided at the alarm control unit, the server device, and/or anothersystem component.

While the present invention has been described with reference tospecific examples, which are intended to be illustrative only and not tobe limiting of the invention, it will be apparent to those of ordinaryskill in the art that changes, additions and/or deletions may be made tothe disclosed embodiments without departing from the spirit and scope ofthe invention.

The foregoing description is given for clearness of understanding only,and no unnecessary limitations should be understood therefrom, asmodifications within the scope of the invention may be apparent to thosehaving ordinary skill in the art.

1. A method of registering a security sensor device with a productdevice to be protected via the security sensor device, the methodcomprising: obtaining first data identifying the security sensor deviceand comprising a first timestamp for an alteration in power delivery tothe security sensor device; obtaining second data identifying theproduct device and comprising a second timestamp for an alteration inpower delivery to the product device; implementing a comparison of thefirst timestamp and the second timestamp; and generating registrationdata for a combination of the security sensor device and the productdevice based on the comparison.
 2. The method of claim 1, wherein thealteration in power delivery to the security sensor device comprises apower connection or disconnection between the security sensor device anda display location via which power is delivered to the security sensordevice.
 3. The method of claim 1, further comprising obtaining positiondata indicative of a location of a product display in which the productdevice is displayed, wherein the registration data associates theposition data with the security sensor device and the product device. 4.The method of claim 3, wherein the position data comprises displaylocation data, the display location data identifying a cradle configuredto receive the security sensor device.
 5. The method of claim 3, whereinthe position data identifies a plan-o-gram position of the location ofthe product display.
 6. The method of claim 3, wherein: the positiondata comprises site location data indicative of a site in which theproduct display is located; and the registration further associates thesite location data with the security sensor device and the productdevice.
 7. The method of claim 1, wherein: the first data and the seconddata comprise sensor power event data and product power event dataindicative of the alteration in power delivery to the security sensordevice and the product device, respectively; the sensor power event datais indicative of whether the alteration in power delivery involveseither a start or an end of power delivery to the security sensordevice; and the product power event data is indicative of whether thealteration in power delivery involves either a start or an end of powerdelivery to the product device.
 8. The method of claim 7, whereinimplementing the comparison comprises determining whether both thesensor power event data and the product power event data match regardingwhether the alteration in power delivery involves either a start or anend of power delivery.
 9. The method of claim 1, wherein: implementingthe comparison comprises determining whether the sensor timestamp andthe product timestamp match; and generating the registration datacomprises associating the sensor data and the product data if thecomparison reveals that the sensor timestamp and the product timestampmatch.
 10. The method of claim 1, wherein: obtaining the sensor datacomprises receiving a sensor data package comprising sensoridentification data and sensor power event data; and obtaining theproduct data comprises receiving a product data package comprisingproduct identification data and product power event data.
 11. The methodof claim 1, wherein obtaining the sensor data comprises receiving asensor data package from the security sensor device via an alarm controlunit at a site in which the product device is located.
 12. The method ofclaim 1, wherein obtaining the product data comprises receiving aproduct data package from the product device via a service executing onthe product device.
 13. A method of registering a security sensor devicewith a product device to be protected via the security sensor device,the method comprising: obtaining a sensor data package comprising sensoridentification data and sensor power event data, the sensor power eventdata being indicative of an alteration in delivery of power to thesecurity sensor device; obtaining position data indicative of a locationof a product display in which the product device is displayed; obtaininga product data package comprising product identification data andproduct power event data, the product power event data being indicativeof an alteration in delivery of power to the product device;implementing a comparison of respective timestamps of the sensor powerevent data and the product power event data; and if the respectivetimestamps match, generating registration data for a combination of thesecurity sensor device and the product device based on the sensoridentification data and the product identification data, theregistration data associating the security sensor device, the locationof the product display, and the product device.
 14. The method of claim13, wherein: implementing the comparison comprises determining whetherboth the sensor power event data and the product power event data matchregarding whether the alteration in power delivery involves either astart or an end of power delivery; and the registration data isgenerated if the sensor power event data and the product power eventdata match regarding whether the alteration in power delivery involveseither a start or an end of power delivery.
 15. The method of claim 13,wherein generating the registration data comprises sending theregistration data to a network storage device for storage of theregistration data in a registration database.
 16. The method of claim15, further comprising storing, in the registration database, customerinteraction data in association with the registration data, the customerinteraction data involving a customer interaction with the productdevice.
 17. A networked computing device for registration of a securitysensor device and a product device to be protected by the securitysensor device, the networked computing device comprising: a processor; amemory in which correlation instructions and database managementinstructions are stored for execution by the processor; a storage deviceconfigured to store registration data associating the security sensordevice and the product device; wherein the processor is configured viathe execution of the correlation instructions to— obtain a sensor dataidentifying the security sensor device and comprising a sensor timestampfor an alteration in power delivery to the security sensor device,obtain product data identifying the product device and comprising aproduct timestamp for an alteration in power delivery to the productdevice, implement a comparison of the sensor timestamp and the producttimestamp, and generate the registration data for the security sensordevice and the product device based on the comparison; and wherein theprocessor is configured via the execution of the database managementinstructions to store the registration data in the storage device. 18.The networked computing device of claim 17, wherein the processor isfurther configured via the execution of the correlation instructions to—obtain position data indicative of a location of a product display inwhich the product device is displayed; and generate the registrationdata such that the registration data associates the location of theproduct display with the security sensor device and the product device.19. The networked computing device of claim 18, wherein the positiondata identifies a plan-o-gram position of the location of the productdisplay.
 20. The networked computing device of claim 17, wherein: thesensor data and the product data comprise sensor power event data andproduct power event data indicative of the alteration in power deliveryto the security sensor device and the product device, respectively; thesensor power event data is indicative of whether the alteration in powerdelivery involves either a start or an end of power delivery to thesecurity sensor device; the product power event data is indicative ofwhether the alteration in power delivery involves either a start or anend of power delivery to the product device; and the processor isfurther configured via the execution of the correlation instructions todetermine whether both the sensor power event data and the product powerevent data match regarding whether the alteration in power deliveryinvolves either a start or an end of power delivery.